Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General spec cleanup #107

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JohnAlbin
Copy link
Contributor

Here's the no-brainer spec clean-up bits (I hope!) from #106. I'll put the other changes in to their own PRs.

I kept them as separate commits, but I can rebase and squash them into 1 commit if you prefer.

@JohnAlbin
Copy link
Contributor Author

Hmm… I just searched the entire repo and .star-given is what is used in the test fixtures. .stars-given is used in the README and SPEC. So, I'm going to guess that .star-given is the "correct" class name and use it consistently throughout.

Also, I've decided I'm going to rebase and squash to 1 commit. There's really not that much changed here.

@JohnAlbin JohnAlbin force-pushed the general-spec-cleanup branch from 5c5493c to b6652c4 Compare January 4, 2015 05:17
@@ -23,7 +23,7 @@ Styleguide 2.1.3.
a.button.star{
...
}
a.button.star.stars-given{
a.button.star.star-given{
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.star-given is what is used in part of the SPEC and everywhere in the test/ directory. Going to assume .stars-given is a typo.

@JohnAlbin
Copy link
Contributor Author

This is good to go now. I've added comments to most of the line changes on the files tab: https://github.com/kneath/kss/pull/107/files

@JohnAlbin
Copy link
Contributor Author

Naturally, there would be a ton of merge conflicts if I pushed all the changes from #106 into your PR queue. So I've queued up all the dependent branches at https://github.com/kss-node/kss/branches/all?query=spec- and I'll push new PRs as we resolve open PRs.

@JohnAlbin
Copy link
Contributor Author

I-maintain-an-open-source-project-too-so-I-totally-understand-youre-not-getting-paid-to-review-my-pull-request-PING! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant